The Cisco multicast switch must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-220462	CISC-RT-000800	SV-220462r622190_rule		Medium

Description
PIM is a routing protocol used to build multicast distribution trees for forwarding multicast traffic across the network infrastructure. PIM traffic must be limited to only known PIM neighbors by configuring and binding a PIM neighbor filter to interfaces that have PIM enabled. If a PIM neighbor filter is not applied to interfaces that have PIM enabled, unauthorized switches can join the PIM domain, discover and use the rendezvous points, and advertise their rendezvous points into the domain. This can result in a denial of service by traffic flooding or in the unauthorized transfer of data.

Description

PIM is a routing protocol used to build multicast distribution trees for forwarding multicast traffic across the network infrastructure. PIM traffic must be limited to only known PIM neighbors by configuring and binding a PIM neighbor filter to interfaces that have PIM enabled. If a PIM neighbor filter is not applied to interfaces that have PIM enabled, unauthorized switches can join the PIM domain, discover and use the rendezvous points, and advertise their rendezvous points into the domain. This can result in a denial of service by traffic flooding or in the unauthorized transfer of data.

STIG	Date
Cisco IOS Switch RTR Security Technical Implementation Guide	2021-03-19

Details

Check Text ( C-22177r508461_chk )
Step 1: Verify that all interfaces enabled for PIM have a neighbor access control list (ACL) bound to the interface as shown in the example below: interface GigabitEthernet1/1 no switchport ip address 10.1.2.2 255.255.255.0 ip pim neighbor-filter PIM_NEIGHBORS ip pim sparse-mode Step 2: Review the configured ACL for filtering PIM neighbors as shown in the example below: ip access-list standard PIM_NEIGHBORS permit 10.1.2.6 If PIM neighbor ACLs are not bound to all interfaces that have PIM enabled, this is a finding.

Check Text ( C-22177r508461_chk )

Step 1: Verify that all interfaces enabled for PIM have a neighbor access control list (ACL) bound to the interface as shown in the example below:

interface GigabitEthernet1/1
no switchport
ip address 10.1.2.2 255.255.255.0
ip pim neighbor-filter PIM_NEIGHBORS
ip pim sparse-mode

Step 2: Review the configured ACL for filtering PIM neighbors as shown in the example below:

ip access-list standard PIM_NEIGHBORS
permit 10.1.2.6

If PIM neighbor ACLs are not bound to all interfaces that have PIM enabled, this is a finding.

Fix Text (F-22166r508462_fix)
Configure neighbor ACLs to only accept PIM control plane traffic from documented PIM neighbors. Bind neighbor ACLs to all PIM-enabled interfaces. Step 1: Configure ACL for PIM neighbors. SW2(config)#ip access-list standard PIM_NEIGHBORS SW2(config-std-nacl)#permit 10.1.2.6 SW2(config-std-nacl)#exit Step 2: Apply the ACL to all interfaces enabled for PIM. SW2(config)#int g1/1 SW2(config-if)#ip pim neighbor-filter PIM_NEIGHBORS

Fix Text (F-22166r508462_fix)

Configure neighbor ACLs to only accept PIM control plane traffic from documented PIM neighbors. Bind neighbor ACLs to all PIM-enabled interfaces.

Step 1: Configure ACL for PIM neighbors.

SW2(config)#ip access-list standard PIM_NEIGHBORS
SW2(config-std-nacl)#permit 10.1.2.6
SW2(config-std-nacl)#exit

Step 2: Apply the ACL to all interfaces enabled for PIM.

SW2(config)#int g1/1
SW2(config-if)#ip pim neighbor-filter PIM_NEIGHBORS